home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
HamCall (October 1991)
/
HamCall (Whitehall Publishing)(1991).bin
/
amateur
/
w0rli
/
mb1202.exe
/
lha
/
SERVER.DOC
< prev
next >
Wrap
Text File
|
1991-02-26
|
7KB
|
240 lines
Server operation: Automatic Export/Import of messages.
The file SERVER.MB contains information that drives the automatic
Export/Import of messages. If the file does not exist, no Export/Import is done.
There are two types of server; "simple" and "complex".
The information required in SERVER.MB, and the type of processing done,
is slightly different for each type.
Simple Server:
A simple server first checks for messages to export. If there are
none, it does nothing. If there were messages to export, it exports them,
and runs the server process. If the server process completes normally,
then an import is done. If the server process does not complete normally,
no import is done. A line like the one below, placed into SERVER.MB, is
all that is required to define a simple server.
S SNAME SNAME.EXE SNAME.OUT fmt SNAME.IN fmt
"SNAME" is the name of the server. Messages addressed to SNAME or SNAME @ SYSOP
will be processed. SNAME.EXE is the name of the server program to execute.
If the server executable has extension EXE or COM, COMMAND.COM is not loaded.
If the server executable has extension BAT, then COMMAND.COM will be loaded,
and about 23k more memory will be required.
To activate the "echo" server, which reads file ECHO.OUT and
creates file ECHO.IN, with ECHO.EXE in directory \MB :
S ECHO \MB\ECHO.EXE ECHO.OUT H8 ECHO.IN H8
Complex Server:
A complex server first exports any messages that match the designators in
the designaotor list. Then the server process is run. Then any generated
messages are imported. Note that, unlike a simple server, all three functions
always take place. Thus a complex server can function (for example) to
transfer messages both ways between the MailBox and smtp.
A list like the one below, placed into SERVER.MB, is required to define a
complex server. If the server file extension is EXE or COM, then COMMAND.COM
is not loaded. If the server file extension is BAT, then COMMAND.COM is
loaded, and you must take it's memory requirement into account.
C SNAME SNAME.EXE SNAME.OUT fmt SNAME.IN fmt
list
*** EOF
Messages will be processed acording to the list, just as in FWD.MB.
Export, Import, and Execute, with no Server process.
Export Only:
O FILE.OUT fmt
list
*** EOF
Import Only:
I FILE.IN fmt
Execute Only:
! FILE
Summary of list types within SERVER.MB
Item Function
C "Activate a Complex server"
I "Input from File"
O "Output to File"
S "Activate a Simple server"
! "Run program or batch file"
Available format modifiers are:
O - Use the old style "standard" (WA7MBL) export/import format.
8 - Use RFC-822 headers.
H - Include the BBS message headers.
If no modifier is given, then ONLY the message text is put into the file.
To Export messages TO the file MSG.OUT in old (WA7MBL) format :
O MSG.OUT O
WA6XXX
*** EOF
To Export messages TO the file MSG.OUT, with only RFC-822 headers
and message text, (as might be used by a user written smtp interface):
O MSG.OUT 8
WA6XXX
*** EOF
To Export messages TO the file MSG.OUT,
with RFC-822 headers, existing BBS headers, and message text :
O MSG.OUT H8
WA6XXX
*** EOF
To Export messages TO the file MSG.OUT, with only the message text :
O MSG.OUT
WA6XXX
*** EOF
To Import messages FROM the file MSG.IN, which is in "standard" format :
I MSG.IN O
DOS commands.
A "!" list is a program or batch file to run. A file extension must be given.
If the extension is BAT, the window size must be large enough for COMMAND.COM
as well as the largest program run from the batch file.
Example:
! CLOCK.BAT
This will run CLOCK.BAT, which can do multiple DOS commands.
! CLOCK.EXE
This will load and run CLOCK.EXE
Wildcards and special "callsigns" in lists.
See WILD.DOC for a description of how to use wildcard characters.
Sublists.
At any place in the SERVER.MB file you can refer to another file.
What happens is that the contents of the sublist are treated exactly
as if they were in the SERVER.MB file. A sublist is given by a line
starting with "@". The rest of the line is the device, path, and file
name of the sublist file.
File formats.
The following is an example export file produced using format H8.
Things to note about this file:
1. There is a blank line following the RFC-822 header, and another
following the MailBox header.
2. The special header item "X-msgtype" is used to show whether the
message is a Bullletin, is Personal, or is an NTS message.
3. The special header item "X-BID" is used to show the BID,
if the message has one.
4. The file can contain multiple messages.
Date: 12 Mar 89 17:09 <- Date at originating MailBox
Message-ID: <8988@N6IYA> <- Message number at orig MailBox
X-msgtype: P <- Message type (B, P, T)
X-BID: 1234_N6IYA <- BID, if the message has one.
From: N6IYA@N6IYA <- User at orig MailBox
To: ECHO@W0RLI.OR.USA.NA <- Full location as sent
Subject: Testing path turnaround. <- Message title
<- Blank between RFC-822 hdr and MailBox hdrs
R:890312/1722z @:W0RLI.OR.USA.NA West Linn #:3571 Z:97068
R:890312/1709z @:N6IYA.CA.USA.NA Felton #:8988 Z:95008
<- Blank between MailBox hdrs and text.
Test message. <- Message text.
../EX <- ".." added, not there in actual format
It appears that there will be a large number of servers created.
These are servers I have heard about. Some are ready for use, some
are in the planning/coding stage.
ECHO - "echo" the message back to sender for path testing.
FILEX - "File eXchange". Upload, Download, directory listings.
INFO - Request BBS info.
REQDIR - Request directory information.
REQFIL - Request a file.
REQQSL - Request qsl manger info for dx callsign.
REQQTH - Request name/address for callsign.
REQWP - Request WP information.
Remote access to the I, I@, IH, and IZ commands.
RLIMON - Automated sysop functions from KJ4LQ.
SMTP - smtp/BBS message interface.
? - Interface with G3PLX AMTOR BBS.
Here is an example for a user-written server, using only DOS batch commands.
This server will print selected messages as they arrive.
1. In the distribution lists for any messages you want printed,
add an extra callsign PRTIT.
2. In SERVER.MB add the lines:
! DEL PRTIT.OUT
O PRTIT.OUT 8
PRTIT
*** EOF
! PRINT PRTIT.OUT